Conversation
|
@Dexnjn I have added a new folder in our shared drive, called "source_cut", This is just a temporay folder, if we all happy with this version, we can use this to replace the current "cut" folder and use it as the starting point of the pipeline. If we are not happy with it, we can still keep the old version. I added a jupyter notebook to show (1) how I made these multi-channel images with proper metadata, (2) how to retrieve meta data and load a specific channel by name. |
|
Will users be forced to define the "physical_pixel_sizes" in the metadata or do we want to include the option to do it manually in the config as well? |
|
Good questions. I think like what we usually do, we just check if physical pixel size is available in the meta data, if yes, use it, if no, check if users have set this in the config. How is that? I think this will be an easy implementation with good flexibility
…________________________________
From: Devon Siemes ***@***.***>
Sent: Tuesday, March 21, 2023 3:31:50 PM
To: MMV-Lab/immun_analysis ***@***.***>
Cc: Jianxu Chen ***@***.***>; Author ***@***.***>
Subject: Re: [MMV-Lab/immun_analysis] add demo (PR #4)
Will users be forced to define the "physical_pixel_sizes" in the metadata or do we want to include the option to do it manually in the config as well?
—
Reply to this email directly, view it on GitHub<#4 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB3TAA7TMAFS67CJA6KOWLDW5G3VNANCNFSM6AAAAAAWCDXSKY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Adapted the workflow to support multi-channel inputs. |
2 participants
demo 1 : how to create multi-channel image with proper meta data
demo 2: how to load metadata and use meta for different purpuses